N4 supports EDIFACT standard CUSCAR message, release D & version 95B.
This specification provides the definition of the Customs Cargo Report message (CUSCAR), an international multi-modal status report message, to be used in Electronic Data Interchange (EDI) between shipping agent and Customs department. The Customs Cargo Report is primarily used by Shipping Companies and Airlines to report full details of cargo carried on vessels. The ship’s agent sends it to Customs. In a terminal, the CUSCAR will be received from the shipping agent.
This message transfers of data from a carrier to a Customs administration for the purpose of meeting Customs cargo reporting requirements. The data provides Customs with a means of "writing off" or acquitting the cargo report against Goods declarations. It also allows Customs to undertake selectivity processing in order to select high risk shipments requiring examination.
The message may be used for reporting:
onward transit/transhipment
short and part shipped goods
empty containers
import/export cargo
house and masterbill relationships
The following sections of this document explain how CUSCAR message is handled in N4 and scope of its implementation.
CUSCAR D 95B Inbound Supported Segments
Following table illustrates the segments of EDIFACT standard CUSCAR D 95B message & scope of each segment in N4.
|
Group |
Segment ID |
Supported Qualifier |
Description |
Supported in N4? |
Mapped Elements |
Reason / Comments |
|---|---|---|---|---|---|---|
|
|
UNB |
|
Interchange Header (sender, receiver) |
Supported |
Interchange Control Reference > InterchangeNumber |
Sender is identified by the contents of the interchange |
|
|
UNH |
|
Message Header (message type, id, version, release number, message reference number) |
Supported |
Interchange Number > msgReferenceNbr |
ID, Version, Release Number is identified by the contents of the interchange |
|
|
BGM |
|
Beginning of message |
Supported |
9 message reference number |
We are handling only original message function in CUSCAR EDI. |
|
|
DTM |
137 |
Date/Time |
Not Supported |
|
msgProducedDateTime is handled in EDI extract and set as current date. Customer needs to use the generic / dynamic flex field if needed to store the date. |
|
|
RFF |
|
Reference |
Not Supported |
|
|
|
|
NAD |
MS |
Sender of the message |
Not Supported |
|
|
|
|
FTX |
|
Free Text |
Not Supported |
|
|
|
SG1 |
TDT |
|
Details of Transport |
Supported |
a) Conveyance Reference Number > inVoyageNbr b) Carrier Identification > shippingLine c) ID means of transport > Vessel Id, Name and Convention |
|
|
|
LOC |
60 |
Place of Arrival |
Not Supported |
|
We will resolve it by facility id. The customer needs to handle in the custom map. |
|
|
DTM |
132 |
Date/Time |
Supported |
a) Data/Time > vessel visit -estimatedTimeArrival |
|
|
|
GIS |
|
General Indicator |
Not Supported |
|
|
|
SG2 - SG3 |
EQD |
CN |
Equipment Details |
Supported |
a) Equipment Identification Number - containerNbr b) Equipment Size/Type - containerISOcode c) Equipment Status - Container Category d) Full/Empty indicator - Container Status |
|
|
|
TSR |
|
Transport Service Requirements |
Not Supported |
|
|
|
|
MEA |
AAE + G |
Measurement |
Supported |
a) measurement unit value - containerGrossWt b) measurement unit qualifier - containerGrossWtUnit |
|
|
|
|
AAE + T |
Measurement |
Supported |
a) measurement unit value - containerTareWt b) measurement unit qualifier - containerTareWtUnit |
|
|
|
DIM |
|
Dimensions |
Not Supported |
|
|
|
|
SEL |
CA, CU, SH |
|
Supported |
a) CA - containerSealNumber1 b) SH - containerSealNumber2 c) CU - containerSealNumber3 |
|
|
|
NAD |
|
Name and Address |
Not Supported |
|
|
|
|
GIS |
|
General Indicator |
Not Supported |
|
|
|
SG3 |
TMP |
|
Temperature |
Not Supported |
|
|
|
|
RNG |
|
Range Details |
Not Supported |
|
|
|
|
CNT |
|
Control Total |
Not Supported |
|
|
|
SG4 (SG4 - SG12) |
CNI |
|
Consignment Information |
Not Supported |
Loop starts from CNI segment |
RFF + BM segment is a mandatory segment and we can get the Bill Of Lading Number from the same |
|
|
CNT |
|
Control Total |
Not Supported |
|
|
|
SG5 (SG5 - SG12) |
RFF |
BM |
Reference |
Supported |
|
Bill Of Lading Number |
|
|
CNT |
|
Control Total |
Not Supported |
|
|
|
|
MOA |
|
Monetary Amount |
Not Supported |
|
|
|
|
LOC |
8, 9, 11, 76 |
Location |
Supported |
Mapped with BL - port informations |
8 - Destination, 9 - Load, 11 - Discharge, , 76 - Origin |
|
|
LOC |
20, 28, 80 |
Location |
Not Supported |
|
|
|
|
GIS |
|
General Indicator |
Not Supported |
|
|
|
|
CUX |
|
Currencies |
Not Supported |
|
|
|
|
CPI |
|
Charge payment instructions |
Not Supported |
|
|
|
SG6 |
TDT |
|
Details of Transport |
Not Supported |
|
|
|
|
LOC |
|
Location |
Not Supported |
|
|
|
|
DTM |
|
Date/Time |
Not Supported |
|
|
|
|
RFF |
|
Reference |
Not Supported |
|
|
|
SG7 (SG7 - SG8) |
NAD |
CN, CZ |
Name and Address |
Supported |
CN - Consignee CZ - Shipper |
|
|
|
NAD |
IV, FW, N1, N2 |
Name and Address |
Not Supported |
|
IV - Invoicee, FW - Freight forwarder N1- Notify Part1, N2- Notify Party2 Customer needs to use the flex fields if needed. |
|
|
RFF |
|
Reference |
Not Supported |
|
|
|
SG8 |
CTA |
|
Contact information |
Not Supported |
|
|
|
|
COM |
|
Communication contact |
Not Supported |
|
|
|
SG9 |
QTY |
|
Quantity |
Not Supported |
|
|
|
|
FTX |
|
Free Text |
Not Supported |
|
|
|
SG10 (SG10 - SG12) |
GID |
|
Goods Item Details |
Supported |
BlItem Holder loop starting segment GID+1+63:BALES 63- blitem quantity Bales - blitem type |
|
|
|
PAC |
|
Package |
Not Supported |
|
|
|
|
HAN |
|
Handling instructions |
Not Supported |
|
|
|
|
FTX |
AAA |
Free Text |
Supported |
commodityNote |
|
|
|
MEA |
AAE |
Measurements |
Supported |
blItem volume and weight |
|
|
|
MOA |
|
Monetary amount |
Not Supported |
|
|
|
|
SGP |
|
Split Goods Placement |
Supported |
|
Added a new attribute quantity in ediBlEquipment element to store the value. |
|
|
DGS |
|
Dangerous Goods |
Supported |
ediBlItem - ediHazard |
|
|
|
PCI |
|
Package Information |
Supported |
ediBlItem - markNumber |
Only one field in the DB model to map marks. We will concatenate all the marks and truncate it if the size is more than 240 |
|
|
CST |
|
Customs Status Of Goods |
Not Supported |
|
|
|
SG11 |
GIS |
|
General Indicator |
Not Supported |
|
|
|
|
DOC |
|
Document / Message Details |
Not Supported |
|
|
|
SG12 |
QTY |
|
Quantity |
Not Supported |
|
|
|
|
FTX |
|
Free Text |
Not Supported |
|
|
|
SG13 |
AUT |
|
Authentication result |
Not Supported |
|
|
|
|
DTM |
|
Date/Time |
Not Supported |
|
|
|
|
RFF |
|
Reference |
Not Supported |
|
|
|
|
UNT |
|
Message Trailer |
Not Supported |
|
|
|
|
UNZ |
|
Interchange Trailer |
Not Supported |
|
|
CUSCAR D 95B Inbound Schema Changes
The following schema changes were made to support CUSCAR:
Added new ediEquipment element of complexType "ediEquipmentDetail" under blTransactions element to create units for the given details (top level EQDs)
Added "packageType" element and added "customerOrderNbr" attribute to ediBlItem complexType.
Added a new "ediBlEquipment" element under "ediBlItem" element to manifest bl item in the specified containers
CUSCAR D 95B Inbound Prerequisites
Following are some pre-requisites for using CUSCAR in N4:
Few EDI files are using special character - apostrophe as segment terminator. The special character is also coming within the data. Ex: FTX+AAA+++MEN?' S SHIRT'. UNA comes with override character. The customer needs to remove the character using load interceptor groovy.
Update message function (ex: update) will not be handled in CUSCAR.
Commodity codes are mandatory to create a BL item but it will not be specified in the CUSCAR. So we added a dummy commodity code which starts with "FAK" in the built-in map. The customer needs to create a custom map to have their own commodity codes for each Bl item.
CUSCAR D 95B Inbound N4 Built-in Map
N4 serves a built-in map which is used to convert CUSCAR Edi message into Navis standard manifest xml. This xml in turn used for further processing.
Following are the related files, part of N4 application and can be downloaded:
cuscar_D_95B.mgt - GoXml map
cuscar.dic - Edifact standard dictionary
manifest.xsd - Navis standard manifest xml schema